Sabre Developer Hub

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Sabre's official read-only MCP server for searching and reading Developer Hub API docs, specs and agent skills.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Sabre Developer Hub": {
      "url": "https://developer.mcp.sabre.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• get_artifact_details read-only

  Returns structured metadata and a list of documentation page links for a Developer Hub artifact. Use the artifact URI returned by look_for_named_sabre_documentation or look_for_artifact_content.

  Parameters:

  • artifactUri (required) — string — The artifact path, e.g. 'rest-api/air-shopping/v1'

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_documentation_page read-only

  Fetches and returns the Markdown or HTML content of a Developer Hub documentation page. Use the page paths listed in the get_artifact_details result.

  Parameters:

  • path (required) — string — The documentation page path ending with .html, e.g. 'air-shopping/overview.html'

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_latest_updated_documentation read-only

  Retrieves a list of the latest updated documentation artifacts in Sabre Developer Hub (https://developer.sabre.com) including their DevStudio URIs, titles, types, versions, update dates, and descriptions.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_spec_file read-only

  Fetches and returns the spec.yml file of a REST API in Sabre Developer Hub (https://developer.sabre.com). Only supports artifact URIs starting with rest-api/. Use the artifact URI returned by look_for_named_sabre_documentation or look_for_artifact_content.

  Parameters:

  • artifactUri (required) — string — The REST API artifact path starting with rest-api/, e.g. 'rest-api/air-shopping/v1'

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• look_for_artifact_content read-only

  Looks for content of APIs, SDKs, Product Collections in Sabre Developer Hub (https://developer.sabre.com) based on a content search query and returns detailed information about matching artifacts including their DevStudio URIs, titles, types, versions, update dates, and content snippets.

  Parameters:

  • searchQuery (required) — string — The search query to find relevant content in Developer Hub artifacts

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• look_for_named_sabre_documentation read-only

  Looks for documentation of APIs, SDKs, Product Collections in Sabre Developer Hub (https://developer.sabre.com) based on a name and returns a list of matching artifacts.

  Parameters:

  • artifactName (required) — string — The name of the artifact to find relevant artifacts in Developer Hub

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_skill read-only

  Returns Sabre Developer Hub agent skills: curated instructions for you (the assistant), published by Sabre, that give you general Sabre knowledge and abilities. Skills cover implementing Sabre APIs (authentication, air search, hotel search), debugging and explaining errors, payloads, and travel-domain behaviour, guided mentoring, and training courses. Call without skillId to list the skills and when to use each one. Call with a skill id to load that skill, then follow its instructions. Call with '<skill-id>/<reference>' to load one of the skill's reference files when the skill tells you to. Check the list before you implement, debug, or explain anything with Sabre APIs, and whenever the user wants to learn Sabre or be taught or mentored. Combine several skills when the task needs it, for example authentication plus air search.

  Parameters:

  • skillId — string — Optional. Omit to list skills. A skill id, e.g. 'new-to-sabre', or a skill reference, e.g. 'new-to-sabre/module-lcc'.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.